OpenEdge Data Management:<br />Database Administration Incremental backup example

This example shows how to use all of the possible incremental backup parameters to perform an incremental offline backup of the devel.db database on UNIX. To perform an online backup, skip Steps 2 through 4.

Prepare the backup media according to the operating system documentation.

Verify that the database is not in use by entering the following command:


proutil devel -C BUSY

Shut down the devel.db database by using the PROSHUT command:


proshut devel

Run PROBKUP -estimate to determine how much media is necessary for the backup:


probkup devel incremental /dev/null -estimate

Enter the following command to perform an incremental offline database backup:


probkup devel /dev/rrm/0m incremental -vs 4000 -bf 20 -verbose -io 1 -com -red 5 -scan

Enter the following command to perform an incremental online database backup:


probkup online devel /dev/rrm/0m incremental -vs 35 -bf 20 -verbose -io 1 -com -red 5

These are the parameters for the commands:


devel

Identifies the name of the database you are backing up.


online

Specifies that the backup is an online backup.


/dev/rrm/0m

Specifies the output destination is a tape drive, /dev/rrm/0m.

Caution: Do not use the same reel of tape that was used for the full backup.


incremental

Specifies that the backup is an incremental backup.


-vs 35

Indicates that the volume size in database blocks is 35. If you do not specify the volume size, PROBKUP fills the entire tape before prompting you for a new tape.


-bf 20

Specifies that the blocking factor is 20.


-verbose

Displays information at 10-second intervals during the backup.


-io 1

Specifies that you can lose one incremental backup and still be able to restore the database. Specifies that all blocks that have changed since the backup before the last backup should be archived.


-com

Indicates that the data should be compressed before it is written to the tape drive. If you specify the -com parameter and do not use -scan, PROBKUP displays the number of blocks and the amount of backup media required for an uncompressed database.

-red 5

Specifies that PROBKUP creates one error-correction block for every five blocks that are backed up.


-scan

Allows the backup utility to scan the database before backing it up to determine the number of blocks to be backed up.

As the incremental offline backup of devel.db executes, the following report appears:

64 bi blocks will be dumped. 13 out of 336 blocks in devel will be dumped. This will require 103424 bytes of backup media. This backup will require a minimum of 400 blocks to restore. 1 volume will be required. Backed up 77 blocks in 00:00:01. Wrote a total of 5 backup blocks using 103424 bytes of media. Backup complete.

64 bi blocks will be dumped. 
13 out of 336 blocks in devel will be dumped. 
This will require 103424 bytes of backup media. 
This backup will require a minimum of 400 blocks to restore. 
1 volume will be required. 
Backed up 77 blocks in 00:00:01. 
Wrote a total of 5 backup blocks using 103424 bytes of media. 
Backup complete.

The number of backup blocks is the number of -bf units written to the tape. Backup blocks contain data, BI, and error-correction blocks.

This example backs up a very small database. Using the -red parameter on a larger database increases the amount of time and backup media required for the backup.

As the incremental online backup of devel.db executes, the following report appears:


Incremental backup started. Backed up 70 blocks in 00:00:01. Wrote a total of 3 backup blocks using 103424 bytes of media. Backup complete.

If you have after-imaging enabled, back up the AI files to a separate tape or disk using a backup utility.